Repository navigation
CI: create the multi-arch manifests 4 targets at a time - #430
Merged
Merged
Conversation
The merge job of a PHP version publishes its 15 targets one after the other: about 22 s each on the main repository, mostly to copy the images to Docker Hub, so 4 to 7 minutes at the end of each run of v5.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The merge job of a PHP version publishes its 15 targets one after the other. On this repository, each target takes
about 22 s, mostly to copy the images to Docker Hub: the merge jobs take 4 to 7.5 min at the end of each run of
v5,against 2 to 3 min before #428 (12 merge jobs, one per variant). They now publish 4 targets at a time.
Test plan (required)
51 s instead of 136 s.
xargs).v5.Checklist